Method and computer system for prefetching of images

ABSTRACT

A method and system for prefetching of data, such as, image data of medical images, for example, digital radiographic images, into a cache. The prefetching relies on workflow information. The method and system is particularly advantageous for use in screening programs where a large number of individuals are screened for a disease, such as cancer, in particular, breast cancer.

CROSS REFERENCES to related Applications

[0001] This application is related to the following patent applications, filed on the same day as this application and assigned to the same assignee, MeVis Technology GmbH & Co. KG

[0002] (1) A method and computer system for screening of medical cases, Serial No. ______; filed May 29, 2001,

[0003] (2) A method and system for in-service monitoring and training for a radiologic workstation, Serial No. ______; filed May 29, 2001,

[0004] which are hereby incorporated by reference to be understood in connection with the present invention.

FIELD OF THE INVENTION

[0005] The present invention relates to a method and apparatus for the operation of a cache buffer store in a data processing system, such as a computer system for rendering of medical images. More particularly, the invention relates to a method and apparatus including a procedure for prefetching of images and a corresponding algorithm for replacing least recently used images from the cache.

BACKGROUND AND PRIOR ART

[0006] In many data processing systems, there is provided between the working memory of the central processing unit and the main memory a high-speed buffer storage unit that is commonly called a “cache”. This unit enables a relatively fast access to a subset of data that were previously transferred from the main storage to the cache, and thus, improves the speed of operation of a data processing system.

[0007] U.S. Pat. No. 4,807,110 discloses a prefetching mechanism for a cache and a two-level shadow directory. When an information block is accessed, a parent identifier derived from the block address is stored in a first level of the shadow directory. The address of a subsequently accessed block is stored in the second level of the shadow directory, in a position associated with the first-level position of the respective parent identifier. With each access to an information block, a check is made whether the respective parent identifier is already stored in the first level of the shadow directory. If it is found, then a descendant address from the associated second-level position is used to prefetch an information block to the cache if it is not already resident therein. This mechanism is to reduce the occurrence of cache misses.

[0008] U.S. Pat. No. 6,154,767 shows a method and apparatus for using attribute transition probability models for prefetching resources. Idle bandwidth of a client is utilized for the prefetching and resource prefetching by the resource server utilizes idle processing and/or data bus resources of the server.

[0009] U.S. Pat. No. 6,151,662 discloses a method of data transaction typing for caching and prefetching. A microprocessor assigns a data transaction type to each instruction. The data transaction type is based upon the encoding of the instruction, and indicates an access mode for memory operations corresponding to the instruction. The access mode may, for example, specify caching and prefetching characteristics for the memory operation. The access mode for each data transaction type is selected to enhance the speed of access by the microprocessor to the data, or to enhance the overall cache and prefetching efficiency of the microprocessor by inhibiting caching and/or prefetching for those memory operations.

[0010] From U.S. Pat. No. 6,098,064 a method for prefetching and caching documents according to a probability ranked need list is known. Documents are prefetched and cached on a client computer from servers located on the Internet in accordance with their computed need probability. Those documents with a higher need probability are prefetched and cached before documents with lower need probabilities. The need probability for a document is computed using both a document context factor and a document history factor. The context factor of the need probability of a document is determined by computing the correlation between words in the document and a context of the operating environment. The history factor of the need probability of a document is determined by integrating both how recently the document was used and the frequency of document use.

[0011] U.S. Pat. No. 6,154,826 discloses a method for maximizing memory system bandwidth by accessing data in a dynamically determined order. The order in which to access said information is selected based on the location of information stored in the memory. The information is repeatedly accessed from memory and stored in the temporary storage until all streamed information is accessed. The information is stored until required by the data processor. The selection of the order in which to access information maximizes bandwidth and decreases the retrieval time.

[0012] Caching is an important technique in all fields of data processing where large amounts of data have to be handled, such as image processing. A particular field of image processing is the rendering, archival, retrieval, processing, transformation, analysis and display of medical images, such as, in the field of digital radiography.

[0013] U.S. Pat. No. 6,041,135 shows an interactive off-line processing method for radiographic images. In this off-line image processing method for radiographic images an image is decomposed into detail images and multiple resolution levels and a residual image; detail images are modified up to a preset resolution level and a processed image is reconstructed by means of the modified detail images and the residual image. Interactive processing is performed with different parameter settings.

[0014] U.S. Pat. No. 6,127,669 discloses a method for computer aided determination of window and level settings for filmless radiology. Input image data is transformed into an image histogram. This histogram is then segmented into a small number of parts corresponding to structures of interest. Segmentation of the histogram is done by a Viterbi optimal runlength-constrained approximation nonlinear filter.

[0015] Window and level settings are calculated to correspond to this segmentation. A readable image of one of the structures of interest is then displayed. In another embodiment, the tool provides a menu of optimal window and level settings corresponding to the different types of information a radiologist may be interested in.

[0016] A common disadvantage of prior art workstations for processing and displaying of digital radiographic images is the latency time experiences by the user of the system when a new image is loaded.

[0017] This is due to the fact that a single digital radiographic image can be over 50 MB in size. For example, in digital mammography a case to be reviewed by a radiologist is composed of about 4 to 8 different images, each 60 MB in size for certain modalities. A complete case thus is about 500 MB of data.

[0018] Even with high-speed processors and memory components such volumes of data result in substantial latency times that are often not acceptable for the users of such workstations. As a consequence, usage of data processing systems for the archiving, transformation, retrieval and transformation of digital radiographic images has been limited so far.

SUMMARY OF THE INVENTION

[0019] Objects of the invention

[0020] It is therefore an object of the present invention to provide an improved method and apparatus for prefetching in order to reduce latency times experienced by a user, in particular with respect to applications for digital radiographic images.

[0021] It is a further object of the invention to provide a method and system having an improved “least recently used algorithm” for freeing a cache memory of image data which is no longer needed.

[0022] It is a still further object to provide such a method and system for coupling to a central picture archiving and communication system (PACS).

[0023] The invention accomplishes the above and other objects and advantages by providing a method and computer system for the prefetching of data, such as image data, for example medical images from the field of digital radiography. The invention enables maximizing system throughput and minimizing latency times experienced by a user. In brief, this is accomplished by taking a predefined workflow into consideration for the prefetching of the images. A corresponding method and system is disclosed in co-pending U.S. patent application entitled A Method And Computer System For Screening Of Medical Cases, Ser. No. ______; filed May 29, 2001,

[0024] This is of particular advantage in so-called “screening programs” where a large number of medical cases is reviewed sequentially by one or a group of radiologists. Typically the cases of such screening programs are all structured in the same or in a similar way. For example each case can consist of the same sequence of image formats and views.

BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The foregoing and other objects and advantages of the invention will become more apparent from the detailed description of the preferred embodiment of the invention described in detail below with reference to the accompanying drawings in which:

[0026]FIG. 1 is a block diagram of a data processing system in accordance with a preferred embodiment of the invention;

[0027]FIG. 2 is a flow chart of the operation of the data processing system of FIG. 1;

[0028]FIG. 3 is an illustration of the structure of an individual medical case;

[0029]FIG. 4 is a block diagram of a digital radiology image workstation in accordance with a second preferred embodiment of the invention;

[0030]FIG. 5 is a block diagram of a digital radiology image workstation in accordance with a third preferred embodiment of the invention;

[0031]FIG. 6 is an illustration of the header of an image;

[0032]FIG. 7 is a flow chart of the operation of a digital radiology image workstation;

[0033]FIG. 8 is a flow chart illustrating the release of an image; and

[0034]FIG. 9 is a block diagram of a number of digital radiology image workstations connected to the same central image server.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0035] The invention will be described in detail as set forth in the preferred embodiments illustrated in the drawings. Although these embodiments depict the invention as in its preferred application, such as, for a digital radiology image system, it should be readily apparent that the invention has equal application to any type of data processing system that encounters or deals with the same or similar problems.

[0036]FIG. 1 shows a data processing system 1 having an application program 2 that is coupled to a cache 3.

[0037] The cache 3 is coupled to a data source 4. The data source 4 can be any type of data source, such as a file system stored on a hard drive or another storage medium or the output of an image processing device, such as a computer aided diagnosis tool.

[0038] The data processing system 1 further has a file 5 for storing a workflow to be performed. The file 5 has a sequence 6 of steps S1, S2, S3, . . . Si, . . . , Sn to be sequentially performed in the workflow. The sequence 6 has a pointer 7 which points to the current step being carried out by the data processing system and/or its user. In the example considered here, the current step to which the pointer 7 is directed, is the step S2.

[0039] A prefetcher 8 has access to the file 5 and is coupled to the cache 3 for requesting of data to be prefetched.

[0040] In operation, the application program 2 reads the sequence 6 to obtain the step to which the pointer 7 is directed. After the application program 2 has obtained the next step to be carried out, it issues a corresponding request to the cache 3 to request data which are required for the performance of the current step.

[0041] These data are transferred from the cache 3 to the application program 2 for display and/or further processing. If a so-called “cache miss” occurs the request for the data is passed to the data source 4 from the cache 3 in order to read the data from the data source 4 and store the data in the cache 3 for access by the application program 2.

[0042] A user of the application program 2 can also input a jump request to jump in the sequence 6 in a forward or backward direction. If such a jump occurs, then the pointer 7 is moved by a corresponding number of steps along the sequence 6.

[0043] In order to prevent the occurrence of cache misses, the prefetcher 8 reads from the sequence 6 the step consecutive to the current step and all remaining images for the current step. In the example considered here the current step is the step S2 and the consecutive step is the step S3. Hence, when the application program 2 works on the current step S2 the prefetcher 8 reads the consecutive step S3 and performs an access operation to the cache 3 in order to request the data which are required for the application program 2 to perform the step S3.

[0044] If the data for carrying out the step S3 is already in the cache 3, no further action is required. If the contrary is the case, the request is transferred to data source 4 in order to provide the cache 3 with the required data.

[0045] When the processing of the current step S2 by the application program 2 is complete, the position of the pointer 7 is incremented by one, such that the pointer 7 points to the consecutive step. The consecutive step S3 is read by the application program 2 and the application program 2 requests the data for the performance of the step S3—which is the new current step—from the cache 3.

[0046] As the corresponding data has been requested previously from the cache 3 by the prefetcher 8 while the application program 2 was busy with the processing of the step S2, it is ensured that the data for the performance of the step S3 is already loaded in cache 3 such that no cache miss occurs. Again the prefetcher 8 performs an access operation to the sequence 6 in order to read the consecutive step of the new current step S3 in order to request the data being required for the performance of the new consecutive step while the current step S3 is being carried out.

[0047] Alternatively the prefetcher 8 can also request the data for a number of consecutive steps or set of steps in the sequence 6 rather than just the data for the next consecutive step.

[0048]FIG. 2 shows a flow chart for illustrating the operation of the data processing system 1 of FIG. 1. In step 41 the application starts working on the current step S_(i); before or after this the prefetcher obtains the current step S_(i) and the next consecutive step S_(i+1) from the workflow in step 42.

[0049] In step 43 the application requests at least a subset of the data required for the performance of the complete step S_(i) from the cache. During the processing of the step S_(i) all of the data required for the performance of step S_(i) is requested by the application in certain discrete data packages.

[0050] After the completion of the processing of the step S_(i) the application goes to the next step S_(i+1) in the workflow in step 44. From there the application jumps to a step S_(i+1+j) in the workflow in the example considered here in response to a corresponding input operation of a user. The step S_(i+1+j) is the new current step. The jump is performed in step 45.

[0051] In parallel, the data required for the performance of the current step S_(i) and the consecutive step S_(i+1) of the current step are requested in step 46 from the cache for the purposes of prefetching. In step 47 it is decided whether the data is already in the cache.

[0052] If this is the case an acknowledgement is sent to the prefetcher in step 48. If the contrary is the case a data source is accessed in step 9 in order to load the data into the cache in step 10. Next an acknowledgement is sent to the prefetcher in step 48. It is to be noted that the step 42 and the steps 46 to 48, 9 and 10 are carried out in parallel to the steps 41 and 43 to 45 with respect to the then current step.

[0053]FIG. 3 shows the structure of a medical case consisting of a number m of images, image 1 to image m. It is assumed that the medical case of FIG. 3 is a standardized case having a predefined number, kinds and formats of images. Such a standardization of medical cases is advantageous for large screening programs where a large number of individuals are examined for a disease, such as cancer, especially breast cancer.

[0054]FIG. 4 is a further preferred embodiment of a data processing system in which like elements are denoted with the same reference numerals as in FIG. 1. File 5 of FIG. 4, which is descriptive of the workflow, contains a case stack 31. The case stack 31 contains a stack of cases, case 1, case 2, case 3, . . . , case N to be reviewed by a radiologist. File 9 a is user definable and contains the sequence of images of interest to the radiologist and the corresponding required format. In the example considered here the radiologist has defined the sequences of images of interest to him in the file 9 a as follows:

[0055] First, the image 1 from the current case is to be displayed in a format 1;

[0056] next, the same image 1 is to be displayed in another format 2;

[0057] next, the image 2 is to be displayed in a format 3;

[0058] next, image m-1 is to be displayed in the format 1; and

[0059] as the last image in the sequence of images to be reviewed for an individual medical case image m is to be displayed in a format 4.

[0060] It is to be noted that image 3 and/or other images of the m images is skipped completely—depending on the user specific initialization of the file 9 a.

[0061] The case stack 31 has a pointer 10 a which points to the current case being processed by the application 2. In the example considered here this is the case 2. Likewise the file 9 a has a pointer 11 pointing to the current image being processed within the current case. In the example considered here the current image is the image 1 (2) of the case 2.

[0062] The application 2 is coupled to a display buffer 12 that is coupled to a monitor 13.

[0063] Further the cache 3 is coupled to a data source manager 14. The data source manager 14 has a table 15 relating image formats (Data Tags) to corresponding data sources. In the example, the format 1 is related to the data source of file reader 16, the format 2 to the scaler 17, the format 3 to CLAHE 18 for performing of a contrast limited adaptive histogram equalization, and format 4 to wavelet enhancement 19.

[0064] In operation, the prefetcher 8 sequentially requests all of the images contained in the current case as indicated by the file 9 a from the cache 3, as well as, the images of the consecutive case. For example, when the prefetcher 8 requests the image 1 (1) of the consecutive case 3, the request is provided to the cache 3. If the corresponding data is already in the cache 3 this is acknowledged to the prefetcher 8.

[0065] If this is not the case, the request is passed onwards to the data source manager 14. The data source manager 14 identifies the appropriate data source for the request, which is the file reader 16. As a consequence, the image 1 (1) of the case 3 is requested from the file reader 16, which reads the corresponding data from mass storage, such as the hard drive of the data processing system 1, not shown in FIG. 4, and transfers the data to the cache 3.

[0066] When the prefetcher 8 requests the image 2 (3) of the case 3, a situation can occur where the image 2 is already in the cache 3, but not in the right format. As the image is not available in the required format the request is still passed onwards to the data source manager 14 for identification of the appropriate data source, which is CLAHE 18 in this case.

[0067] As a consequence, the CLAHE 18 is requested to provide the image 2 in the required format 3. This is done by the CLAHE 18 by requesting the corresponding image data in the format 1 from the cache 3, and then performing the contrast limited adaptive histogram equalization on the raw image data. The resulting transformed raw image data is stored in the format 3 in the cache 3 and an acknowledgement is send to the prefetcher 8.

[0068]FIG. 5 shows a further preferred embodiment of the data processing system. Again the same reference numerals will be used for like elements corresponding to elements of FIG. 1 and 4.

[0069] The application program 2 is coupled to the prefetcher 8 to inform the prefetcher 8 of a next case to be processed. Again the prefetcher requests the images required for the current case and a consecutive case from the image cache 3.

[0070] If a requested image is not in the image cache 3, the request is passed onwards to the image source 20. The operation of image source 20 corresponds to the data source manager 14. The image source 20 identifies an appropriate image source such as file reader 16 or scaler 17 or passes the request onwards to enhancement component 21, which passes the request onwards to CLAHE 18 or wavelet transformer 19 depending on the required image enhancement.

[0071] The requested image is loaded and/or generated by the respective image source and the image is stored in the image cache 3. This is acknowledged by the data source, which has loaded and/or generated the requested image by the message “Req_done” to all requestors of the image.

[0072] If a requestor of the image does not require the image anymore, a “release” message is sent to the image cache 3 from the requestor. Likewise a “cancel” message can be sent to the image cache 3 in case a request is to be cancelled before it has been completed. Such a situation can occur when the user jumps to another case in the case stack.

[0073]FIG. 6. shows the format of an image file 22 having a header 23 and a field 24 for storage of the pictorial data.

[0074] The header 23 contains an entry for the case number to which the image belongs, the image number for identification of the image, the image format, the requestors, the priority of the image for the purposes of a least recently used algorithm and a lock count. The utilization of those fields will become more apparent in the following.

[0075]FIG. 7 shows a flow chart for illustrating a least recently used algorithm and the generation of the header 23 of an image. In step 70 an image I_(k) of a case i is requested by a requester. In principle each of the components of the data processing system can take the role of a requestor of an image. This applies both to the application program as well as to the prefetcher and the data sources.

[0076] Also, the application program can have more than one requestor. For example individual program components of the application program can take the role of individual requestors of images.

[0077] In step 71 the corresponding request is sent to the cache. In step 72 the cache decides whether the requested image is already available. If this is the case the lock count is incremented in step 73. In step 74 the priority of the image is incremented by +P₂. For example, the value of P₂ can be equal to 100. In step 75 an acknowledgement is sent to all requestors of the image; the requestors are identified by the corresponding data field in the header 23 of the requested image.

[0078] If the image is not in the cache the control goes to step 76 for generation of a header of the image in the cache. The priority of the image is set to be equal to a predefined value of P₁ in step 77. For example the value of P₁ can be equal to 100. In step 78 the lock count is set to be equal to 1.

[0079] In step 79 it is decided whether the cache has enough capacity for loading of the pictorial data of the requested image. If this is the case the pictorial data are requested from the appropriate image source in step 80. In step 81 the pictorial image data are loaded and/or generated by the image source.

[0080] This can require that the image source itself issues a request for the image in an appropriate format, for example to calculate the desired transformation in the requested image format. For example, if the image source is CLAHE, the CLAHE requires raw image data in the format 1. Correspondingly, the CLAHE requests the image in the format 1 such that the steps from step 70 onwards are invoked.

[0081] Once the requested image is present in the cache in the raw data format 1, the CLAHE image transformation is carried out to generate the image in the requested format 3. This way the step 81 is completed and an acknowledgement is provided to all requestors of the image in the format 3 in step 82.

[0082] If it is decided in step 79 that the cache does not have enough capacity, the control goes to step 83. In step 83 the contents of the cache is examined for images having a lock count equal to 0. All images having a lock count equal to 0 are grouped into a set S.

[0083] In step 84 an image I_(L) of the set S having the lowest priority of the images in the set S is identified. This image I_(L) is freed from the cache in step 85.

[0084] In step 86 all priorities of the images of the set S are decremented by one but not below 0. From 86 the control returns back to step 79 in order to repeat the step 83 to 86 if the available cache capacity is still insufficient.

[0085] The flow chart of FIG. 8 shows the steps performed when a requestor releases a previously requested image or cancels a request. In step 80 a of FIG. 8, the requestor releases the image I_(k) of case i because the requestor does not require the image anymore.

[0086] In step 81 a, a corresponding release message is received by the image cache and the header of the image I_(k) is identified in order to decrement the lock count in the header. This is done in step 81 a. In step 82 a, the priority is decremented by P₃ but not below 0. For example, the value of P₃ can be equal to 50. This way the released image can be replaced or removed from the cache in case capacity needs to be provided. The replacement is done in accordance with the least recently used algorithm as illustrated with respect to FIG. 7, in particular steps 83 to 84.

[0087]FIG. 9 shows a system having a number of radiographic workstations 25 corresponding to the data processing system 1 of FIG. 1, 4 and 5. The workstations 25 are coupled to an image server 26. The image server 26 has a central archive for medical images.

[0088] Each of the workstations 25 has the components of the data processing system 1 of FIG. 4. In addition each workstation 25 has a scheduler 28 that is connected to the case stack 31 and a keyboard 27 for entering jump commands and other entries. Further the workstation 25 has a local storage 29 for the storage of image data provided by the image server 26 and a user profile 30.

[0089] In operation the scheduler 28 identifies the case to be processed from case stack 31 and requests the corresponding image data from the image server 26. Preferably this is done when the workstation is not in use by the radiologist such as during night time.

[0090] This way the required data can be downloaded from the image server 26 over night, which takes a considerable amount of time in view of the large data volume. The image data is captured and stored on the storage 29 locally on the workstation 25. When the cases of the case stack 31 are reviewed by the radiologist, the required image data is obtained directly from the storage 29 and not from the image server 26 which further reduces latency times.

[0091] Although the present invention has been shown and described with respect to preferred embodiments, nevertheless, changes and modifications will be evident to those skilled in the art from the teachings of the invention. Such changes and modifications that embody the spirit, scope and teachings of the invention are deemed to fall within the purview of the invention as set forth in the appended claims.

List of Reference Numerals

[0092] data processing system  1 application program  2 cache  3 data source  4 file  5 sequence  6 pointer  7 prefetcher  8 file  9a pointer 10a pointer 11 display buffer 12 monitor 13 data source manager 14 table 15 file reader 16 scaler 17 CLAHE 18 wavelet transformer 19 image source 20 enhancement component 21 image file 22 header 23 pictorial data 24 workstation 25 image server 26 keyboard 27 scheduler 28 storage 29 user profile 30 case stack 31 

What is claimed is:
 1. A method for prefetching of images, the method comprising the steps of: (a) providing a first file descriptive of a sequence of images required for carrying out a predetermined workflow, the first file comprising a reference for each of the images; (b) providing a first pointer for pointing to a current image of the sequence of images; (c) reading the reference of at least one subsequent image of the sequence of images which is subsequent to the current image in the workflow; and (d) prefetching of the subsequent image by means of its corresponding reference.
 2. The method of claim 1 further comprising the steps of: (e) providing a second file descriptive of a number of cases to be sequentially processed in the workflow; (f) providing a third file being descriptive of a sequence of images required for the processing of each individual case.
 3. The method of claim 2 further comprising providing a second pointer for pointing to a current case of the number of cases to be sequentially processed.
 4. The method of claim 1 whereby the first file comprises first data descriptive of an image format.
 5. The method of claim 1 whereby the first file comprises second data descriptive of an image processing operation.
 6. The method of claim 1 further comprising the step of assigning a priority to the subsequent image when the prefetching is performed.
 7. The method of claim 1 comprising the further steps of caching prefetched images in an image cache, and removing prefetched images from the image cache by a least recently used algorithm.
 8. The method of claim 1 comprising the further step of generating an image header for storage in a cache when the prefetching is performed.
 9. The method of claim 8 wherein the header contains second data being descriptive of the required image format, an image processing operation, the priority of the image and a lock count for locking the image in the cache.
 10. A method for prefetching of medical images from an image source, the method comprising the steps of: (a) providing a case stack descriptive of a number of medical cases to be processed, each of the cases having assigned a predetermined number of medical images; (b) providing a user definable file identifying the set of the images of each case to be sequentially rendered; (c) prefetching of the set of images of a current case and prefetching of the set of images of a consecutive case into a cache from the image source.
 11. The method of claim 10 wherein the user definable file comprises first data for indicating a required format of a respective image of the set of images.
 12. The method of claim 10 wherein the user definable file comprises second data for specifying an image processing operation to be performed on the corresponding image of the set of images.
 13. The method of claim 12 wherein the image processing operation is selected from the group consisting of scaling, CLAHE and wavelet enhancement.
 14. The method of claim 10 comprising the further step of generating a header for each image to be prefetched, the header comprising an image reference of the said image to be prefetched, a priority, a lock count and a requestor of the image.
 15. The method of claim 14 comprising the further step of increasing the priority by a first number for each additional requestor.
 16. The method of claim 14 comprising the further step of reducing the priority by a second number for each release or cancellation of a requestor.
 17. The method of claim 14 comprising the further steps of incrementing the lock count with each additional requestor and decrementing the lock count when a request is released or cancelled.
 18. A computer system for rendering of medical images comprising (a) an application program having at least one requestor program component for requesting of images; (b) a workflow file for specifying a sequence of images to be processed; (c) a cache memory coupled to the application program; (d) a prefetcher program component being coupled to the cache memory and to the workflow file; and (e) a data source for providing images to the cache memory; the prefetcher program component enabling prefetching of at least one subsequent image of the sequence of images to be processed as indicated by the workflow file.
 19. The computer system of claim 18 wherein the workflow file comprises a case stack for identifying a number of medical cases to be processed and a user definable file for identification of a set of images to be sequentially processed for each one of the cases, and wherein the prefetcher program component is enabled to prefetch the set of images of a current case and the set of images of another case as indicated by the case stack.
 20. The computer system of claim 18 wherein the cache memory has a cache program component for routing of a request of an image to an appropriate data source.
 21. The computer system of claim 18 further comprising a cache program component for generating header data for each image requested from the cache memory, the header data comprising a priority, a lock count and an image format for selection of a data source.
 22. The computer system of claim 18 further comprising a scheduler coupled to a remote image server via a communication link, the remote image server containing a database of images and the scheduler being enabled to initialized a loading operation from the image server to a local file system of the images required for carrying out the workflow as indicated by the workflow file. 